|
This is a list of tutorials which are available through IBM Software Group Services. Please, contact your IBM representative in case of further interest.
|
List of Expeditor integrator tutorials and workshops offered by IBM Software Group Services:
Part 2 - Extend messaging infrastructure to devices using micro broker and Expeditor integratorPart 2b – Extend JMS Messaging to In-store devices Part 4 – Developing a Expeditor integrator Custom ActivityExpeditor integrator contains a flexible flow engine for simple successive execution of its activities within transactional context. This part of the Expeditor integrator tutorial series demonstrates how to develop a Custom Activity for Expeditor integrator flows (Application Control Flows being executed by the ACS Service = mini flow engine). Custom Activity deployment and integration into a custom Flow definitions is also shown.
Part 5 – Introduction to IBM WebSphere Message BrokerWith IBM WebSphere Message Broker being the most common back-end target for Expeditor integrator, this tutorial provides a short introduction to back-end flow development. Simple flows are created which can receive messages from Expeditor integrator.
Part 6/7 – Extend JMS Messaging to in-store devicesUsing the coded Messaging Client from tutorial series 2a, this tutorial offers two end-to-end tests. The first demo environment demonstrates a simple test from the Messaging Client over Expeditor integrator to a MQ Server back-end. The second demo environment is the reversed counterpart of this setup.
Part 7 - De-central scenarios (1) The scenarios described in part 5 provide an understanding of an end-to-end use case implementation which bridges a different communication technology to messaging (HTTP). The set-ups provided use a step-by-step approach including the full round-trip messaging implementation for device (client) <-> back-end (server) communication. A de-central messaging hub / server is used to transform/pre-process messages for efficient communication with the back-end. The following steps are explained: forwarding messages to the back-end, writing incoming XML messages to the de-central server's database, retrieving XML data from HTTP source and reading and forwarding data from the de-central server's database. Part 6 - De-central scenarios (2) Chapter 6 of the tutorial series explains two advanced scenarios in which Expeditor integrator can be applied. The first example takes a look at utilization of two Expeditor integrator instances and the corresponding configuration for the communication between them. The second set-up demonstrates how to leverage the publish/subscribe feature by bridging topics between WebSphere MQ v7 back-end and the Expeditor integrator runtime. Part 8 – Enabling Expeditor integrator SecurityExpeditor integrator provides different security layers. The transport layer can be secured by using TLS/SSL between IBM micro broker clients and Expeditor integrator's micro broker and between integrator's micro broker bridge and MQ Server (Broker) in the back-end. Access to local micro broker resources can be controlled (ACL configuration). Furthermore, Expeditor integrator offers options for securing ACS flows and ACS Activity execution. How this can be achieved is described in this part of the tutorial series.
Note: There is an end-to-end messaging security guide based on TLS/SSL freely available through IBM developerWorks: Messaging security guide for IBM Lotus Expeditor 6.2.3 integrator software |